Methods and systems for facilitating charging sessions for electric vehicles

ABSTRACT

Embodiments of a method and/or system for charging one or more electric vehicles (e.g., based on one or more reserved charging sessions; for charging an electric vehicle during a scheduled time period; etc.) can include: receiving a reservation request (e.g., a reservation request including one or more reservation parameters; etc.); scheduling a reserved charging session based on the reservation request (e.g., based on reservation parameters from the reservation request; etc.); determining a check in at an Electric Vehicle Service Equipment (EVSE) for the reserved charging session; and/or causing the EVSE to charge the electric vehicle based on the reserved charging session (e.g., during the scheduled time period; etc.).

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/843,874 filed on Apr. 8, 2020, which is a continuation-in-part ofU.S. patent application Ser. No. 16/741,712, filed on Jan. 13, 2020 andnow issued as U.S. Pat. No. 10,836,274 issued on Nov. 17, 2020, whichare each incorporated in its entirety herein by this reference.

TECHNICAL FIELD

The disclosure generally relates to charging of electric vehicles.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 includes a flowchart representation of variations of anembodiment of a method;

FIG. 2 includes a flowchart representation of variations of anembodiment of a method;

FIG. 3 includes a flowchart representation of variations of anembodiment of a method.

FIG. 4 includes a flowchart representation of variations of anembodiment of a method.

FIG. 5 includes a flowchart representation of variations of anembodiment of a method.

FIG. 6 includes a specific example of a flowchart representation of loadmanagement in variations of an embodiment of a method.

FIG. 7 includes a flowchart representation of variations of anembodiment of a method.

FIG. 8 includes a specific example of a flowchart representation ofvariations of an embodiment of a method.

FIG. 9 includes a specific example of fleet management, such as whereenergy needed (e.g., in kWhs) can be predicted for any fleet job pairedwith a unique driver.

DESCRIPTION OF THE EMBODIMENTS

The following description of the embodiments (e.g., including variationsof embodiments, examples of embodiments, specific examples ofembodiments, other suitable variants, etc.) is not intended to belimited to these embodiments, but rather to enable any person skilled inthe art to make and use.

1. Overview

As shown in FIGS. 1-3 , embodiments of a method 100 for charging one ormore electric vehicles (e.g., based on one or more reserved chargingsessions; for charging an electric vehicle during a scheduled timeperiod; etc.) can include: receiving a reservation request (e.g., areservation request including one or more reservation parameters; etc.)Silo; scheduling a reserved charging session based on the reservationrequest (e.g., based on reservation parameters from the reservationrequest; etc.) S120; determining a check in at an Electric VehicleService Equipment (EVSE) for the reserved charging session S130; and/orcausing the EVSE to charge the electric vehicle for the reservedcharging session (e.g., during the scheduled time period; etc.) S140.

Additionally or alternatively, embodiments of a method 100 can include:facilitating an ad hoc charging session S150; providing a user interfaceS160; and/or providing notifications S170. However, embodiments of themethod 100 can include any suitable processes for facilitating chargingof one or more electric vehicles.

In a specific example, as shown in FIGS. 2-3 , the method 100 (e.g., forcharging a first electric vehicle during a scheduled time period and/orfor charging a second electric vehicle during an ad hoc time period;etc.) can include: receiving a reservation request from a first user ata first user device (e.g., at a mobile application for the first userdevice; etc.), such as where the first user is associated with the firstelectric vehicle, and such as where the reservation request includes atleast one reservation parameter indicative of the scheduled time period;scheduling a reserved charging session for the first user based on theat least one reservation parameter; determining eligibility for an adhoc charging session for the second electric vehicle at an ElectricVehicle Service Equipment (EVSE) during the ad hoc time period prior tothe scheduled time period (e.g., based on a comparison between the adhoc time period and the scheduled time period; etc.); causing the EVSEto charge the second vehicle based on an integration with the EVSE(e.g., after determining eligibility for the ad hoc charging session;after determining that the user is eligible for the ad hoc chargingsession; etc.); determining a check in at the EVSE for the reservedcharging session (e.g., after the ad hoc charging session for the secondelectric vehicle; etc.); and/or causing the EVSE to charge the firstelectric vehicle during the scheduled time period based on theintegration with the EVSE (e.g., in response to determining the check inof the first electric vehicle at the EVSE, etc.).

As shown in FIG. 4-5 , embodiments of a method 300 (e.g., for chargingan electric vehicle for a charging session, etc.) can include: receivinga reservation request from a first user at a first user device for afirst charging session, wherein the first user is associated with thefirst electric vehicle, and wherein the reservation request comprises atleast one reservation parameter indicative of the charging session forthe first electric vehicle S310; determining eligibility for a powerdistribution type for the first charging session at the first ESVE(e.g., in response to receiving the at least one reservation parameter,etc.) S320; determining a first check in at the first EVSE for the firstcharging session S330; causing the first EVSE to charge the firstelectric vehicle based on a first integration with the EVSE S340;causing the first EVSE to continue charging the first electric vehiclein accordance with the power distribution type for the first chargingsession (e.g., after determining the first check in at the first EVSEfor the first charging session, etc.), based on a second integrationwith the EVSE S350.

In a specific example, as shown in FIG. 6 , the method 300 can includedirectly controlling load management for one or more EVSEs (e.g., viaOCPP and/or other suitable protocols, such as protocols describedherein, etc.), where controlling load management can include causingpower throttling between 0 and the max capacity for each of the one ormore EVSEs.

As shown in FIG. 7 , embodiments of a method 400 (e.g., for charging afirst electric vehicle at an EVSE), can include: receiving a reservationrequest from a first user at a first user device for a first chargingsession S410 (e.g., wherein the first user is associated with the firstelectric vehicle, and wherein the reservation request comprises at leastone reservation parameter indicative of the first charging session forthe first electric vehicle; etc.); determining a first check in at thefirst EVSE for the first charging session S420; issuing, via a chargermanagement system, a code for authentication between the first electricvehicle and the first EVSE S430; causing the first electric vehicle tocommunicate the code to the first EVSE based on allowance anddisallowance of charging S440; and/or completing authentication inresponse to receipt of the code by the first EVSE S450.

In a specific example, as shown in FIG. 1 , the method 100 (e.g., forcharging an electric vehicle for a reserved charging session, etc.) caninclude: receiving a reservation request including a reservationparameter indicative of a scheduled time period; scheduling the reservedcharging session based on the reservation parameter; determining a checkin of the electric vehicle at an EVSE for the reserved charging session;and causing the EVSE to charge the electric vehicle in association withthe scheduled time period based on an integration with the EVSE (e.g.,in response to determining the first check in of the electric vehicle atthe EVSE, etc.).

Embodiments of the method 100 and/or the system 200 can function toenable any EVSE (e.g., any charging equipment) to handle ad hoc and/orreserved charging. Embodiments can function to improve user experiencewith charging electric vehicles by improving interoperability,reliability (e.g., where reservations can guarantee charging sessions atone or more EVSEs, etc.), and/or better utilization of publicinfrastructure. However, embodiments can include any suitablefunctionality.

In examples, the system and/or method can confer at least severalimprovements over conventional approaches. Specific examples of themethod 100, 300 and/or system 200 can confer technologically-rootedsolutions to issues associated with charging electric vehicles.

In specific examples, the method 100 and/or system 200 can improve lowinteroperability between different charging networks each requiring adifferent mode of access to receive charging (e.g., requiring anelectric vehicle user to install and use multiple applications, RFIDcards, etc.). In specific examples, the method 100, 300 and/or system200 can improve low utilization of deployed EVSEs, such as where lowutilization can be caused by gas cars parked at EVSEs, deployment of anEVSE at a low-traffic location, avoidance of public charging by usersdue to difficulty of access and/or unpredictable availability, and/orother suitable causes. In specific examples, the method 100, 300 and/orsystem 200 can improve unpredictability associated with a first comefirst serve model for using EVSEs, where such unpredictability can leadto long wait times or having to extensively search for an open EVSE.

In specific examples, the method 100, 300 and/or system 200 can improvevarious areas associated with electric vehicle charging, including oneor more of: shared workplace charging, shared home charging inmulti-unit dwellings, shared public place charging (e.g., for fasterchargers with charging session limits; for lifestyle charging wherecharging sessions can be completed in a manner that complements a user'slifestyle and/or schedule; etc.); road trip planning; towing (e.g., fortowing a stranded electric vehicle to an EVSE that can be reservedbefore arrival; etc.); fleets and/or ridesharing electric vehicles(e.g., delivery fleets, transport fleets, and/or ridesharing electricvehicles that can reserve one or more EVSEs; for avoiding downtime;etc.); V1G unidirectional charging (e.g., enabling users to reservecertain EVSEs during event hours to curtail load; reserving and/orthrottling L2 EVSEs into L1 EVSEs during event hours to curtail load;etc.); Vehicle to Grid (V2G) charging (e.g., enabling bi-directionalEVSEs that can supply electricity back to the grid to also serviceelectric vehicles in normal conditions; enabling reservations forvehicles able to respond to demand response events via one or morebi-directional EVSEs; etc.); autonomous electric vehicles (e.g., whichcan be configured to make reservations for one or more scheduledcharging sessions; which can be aided by human individuals who can plugin the EVSE for the autonomous electric vehicle; etc.); and/or any othersuitable areas.

In specific examples, the technology can transform entities (e.g.,EVSEs, electric vehicles; etc.) into different states or things. Inspecific examples, the method 100, 300 and/or system 200 can cause oneor more EVSEs to charge one or more electric vehicles, such as for oneor more reserved charging sessions and/or ad hoc charging sessions. Inspecific examples, the method 100, 300 and/or system 200 can facilitatethe charging of an electric vehicle from a partially charged state orempty state to a fully charged or to a more fully charged state.

Additionally or alternatively, data described herein (e.g., reservationrequests; reservation parameters, EVSE reservation parameters; EVSEidentifiers; other EVSE data; user identifiers; vehicle identifiers;other identifiers; user interface data; user data; electric vehicledata; reserved charging session-related data; ad hoc chargingsession-related data; etc.) can be associated with any suitable temporalindicators (e.g., seconds, minutes, hours, days, weeks, time periods,time points, timestamps, etc.) including one or more: temporalindicators indicating when the data was collected, determined,transmitted, received, and/or otherwise processed; temporal indicatorsproviding context to content described by the data; changes in temporalindicators (e.g., data over time; change in data; data patterns; datatrends; data extrapolation and/or other prediction; etc.); and/or anyother suitable indicators related to time.

Additionally or alternatively, parameters, metrics, inputs, outputs,and/or other suitable data can be associated with value types including:scores, confidence levels, identifiers, values along a spectrum, and/orany other suitable types of values. Any suitable types of data describedherein can be used as inputs (e.g., for different models describedherein, such as scheduling models for scheduling one or more reservedcharging sessions and/or in relation to one or more ad hoc chargingsessions; etc.), generated as outputs (e.g., of models), and/ormanipulated in any suitable manner for any suitable componentsassociated with the method 100, 300 and/or system 200.

One or more instances and/or portions of the method 100 and/or processesdescribed herein can be performed asynchronously (e.g., sequentially),concurrently (e.g., performing scheduling for a plurality of reservedcharging sessions and/or ad hoc charging sessions for a plurality ofEVSEs across a plurality of locations, for a plurality of users andassociated electric vehicles; performing processes of the method 100concurrently on different threads for parallel computing to improvesystem processing ability for facilitating reserved charging sessionsand/or ad hoc charging sessions; etc.), in temporal relation to atrigger event (e.g., performance of a portion of an embodiment of themethod 100), and/or in any other suitable order at any suitable time andfrequency by and/or using one or more instances of the system 200,components, and/or entities described herein.

Embodiments of the system 200 can include a reservation system (e.g.,for scheduling and/or implementing one or more reserved chargingsessions and/or ad hoc charging sessions; for maintaining reservationcalendars for EVSEs; for communicating with one or more EVSEs to causecharging of one or more electric vehicles; a centralized reservationsystem; etc.); an application (e.g., a mobile application for a mobileuser device; an application including a user interface, such as forreceiving inputs from a user and/or for providing information to a user;etc.); and/or other suitable components. In variations, the system 200can include one or more EVSEs, electric vehicles, and/or any othersuitable components. Components of embodiments of the system 200 caninclude any suitable distribution of functionality across thecomponents.

The system 200 and/or portions of the system 200 can entirely orpartially be executed by, hosted on, communicate with, and/or otherwiseinclude: a remote computing system (e.g., a server, at least onenetworked computing system, stateless, stateful; etc.), a localcomputing system, user devices, electric vehicles, EVSEs and/or othersuitable charger equipment, mobile phone device, other mobile devices,personal computing device, tablet, wearable devices, databases,application programming interfaces (APIs) (e.g., for accessing datadescribed herein, etc.) and/or any suitable component. Communication byand/or between any components of the system can include wirelesscommunication (e.g., WiFi, Bluetooth, radiofrequency, Zigbee, Z-wave,etc.), wired communication, and/or any other suitable types ofcommunication.

The components of the system 200 can be physically and/or logicallyintegrated in any manner (e.g., with any suitable distributions offunctionality across the components, such as in relation to portions ofthe method 100; etc.). In specific examples, any suitable components ofembodiments of the system 200 can perform any suitable portions ofembodiments of the method 100 and/or 300. However, the method 100, 300and/or system 200 can be configured in any suitable manner.

2.1 Receiving a Reservation Request.

Embodiments of the method 100 and/or 300 can include receiving areservation request S110 and/or S310, which can function to receiveinformation regarding a request for a reserved charging session (and/orad hoc charging session; etc.).

Reservation requests are preferably digital requests received (e.g.,wirelessly received; etc.) from a user at a user device. In a specificexample, a reservation request can be received via a mobile applicationexecuting on a mobile user device of a user associated with an electricvehicle. In a variation, one or more reservation requests can be made atan EVSE (e.g., at a user interface of the EVSE; etc.). However,reservation requests can be made at any suitable location by anysuitable devices and/or entities.

Reservation requests can be made from an entity remote from the EVSE(s)and/or charging location(s) that are requested. Additionally oralternatively, reservation requests can be made from an entity proximal(e.g., at; located near; close to; etc.) the EVSE(s) and/or charginglocation(s) that are requested, such as for an ad hoc charging session(e.g., a charging session for a current time at a proximal EVSE, etc.).However, reservation requests can be by entities at any suitabledistance from EVSEs and/or charging locations.

Reservation requests can be manually made (e.g., by a user) and/orautomatically made (e.g., by autonomous electric vehicles and/ornon-autonomous electric vehicles, such as based on predefined rules; byany suitable computing devices; by a centralized reservation system;etc.). However, reservation requests can be made and/or received in anysuitable manner.

Reservation requests are preferably received at a reservation system(e.g., a centralized reservation system; etc.), such as a reservationsystem that receives (and/or processes) reservation requests from aplurality of users for a plurality of EVSEs for charging a plurality ofelectric vehicles. Additionally or alternatively, reservation requestscan be received at any suitable component (e.g., directly at an EVSE,etc.).

Reservation requests preferably include one or more reservationparameters indicating information (e.g., a scheduled time period for acharging session; location data; user data; etc.) regarding therequested charging session. Reservation parameters preferably include atleast one of: reservation start time (e.g., start time for a chargingsession; etc.); reservation end time (e.g., end time for a chargingsession; etc.); and location (e.g., location of a user relative an EVSEand/or charging location; location coordinates of a user; such as basedon location of a corresponding user device; such as based on GPScoordinates of a user device; etc.). Additionally or alternatively,reservation parameters can include any one or more of: destination data(e.g., requested destination for a charging location; etc.); origin data(e.g., current location data; etc.); EVSE data (e.g., data indicating arequested EVSE and/or associated information; data describing the EVSE,such as type of EVSE; a physical identifier; location of the EVSE;etc.); user data (e.g., user account information; location information;etc.); electric vehicle data (e.g., describing an electric vehicle to becharged in a reserved charging session; etc.); charging session data(e.g., requested charging features; etc.); location requests (e.g.,indicating requested charging locations and/or EVSE(s); requested nearbyinstitutions such as markets, restaurants, etc., nearby to the charginglocation; etc.); and/or any other suitable reservation parameters.

In a specific example, a reservation request can include a set ofreservation parameters including a reservation start time for thereserved charging session; a reservation end time for the reservedcharging session; and a location parameter indicating distance between auser (e.g., based on location of a user device; etc.) and a chargingsession location associated with the EVSE (e.g., a location of the EVSE;location coordinates for the EVSE; a general charging session locationassociated with a set of EVSEs including the EVSE; etc.).

In examples (e.g., specific examples concerning ad hoc chargingsessions, etc.), a reservation request (e.g., from a user requesting anad hoc charging session for an EVSE at a current time period, etc.) caninclude ad hoc reservation parameters including a reservation start timeindicating a current time period (e.g., the current time at the time ofthe request; etc.), a reservation end time (e.g., end time for the adhoc charging session, etc.), and/or a location parameter indicating acurrent location (e.g., of the user and/or user device at the time ofrequest; such as based on current GPS location of the user device;etc.). In a specific example, a reservation request (e.g., for areserved charging sessions; etc.) can include at least one reservationparameter including a first reservation start time for the reservedcharging session, a first reservation end time for the reserved chargingsession, and a first location parameter (e.g., indicating distancebetween a first user and a charging session location associated with theEVSE; etc.); and where an ad hoc charging session can be associated witha set of ad hoc reservation parameters including a second reservationstart time indicating a current time period, a second reservation endtime for the ad hoc charging session, and a second location parameterindicating a current location of a second user associated with a secondelectric vehicle.

In examples (e.g. a specific example concerning charging sessions,etc.), a reservation request (e.g., from a user requesting a chargingsession for an EVSE, etc.) can include at least one power distributionparameters and/or other suitable reservation parameters indicative ofhow the EVSE implements charging of the electric vehicle. In examples,power distribution parameters can be implemented independent ofparameters included in a reservation request (e.g., determining anoptimal charging method to enable smooth fleet operations; etc.). Powerdistribution parameters can include one or more of a solar productionparameter (based on the solar production by the EVSE during the chargingsession or at a period of time, etc.); an infrastructure-limitationparameter (e.g., obtained from data describing the EVSE, such as type ofEVSE and location of the EVSE, etc.); a time-of-use parameter (e.g., forV1G unidirectional charging enabling users to reserve certain EVSEsduring event hours to curtail load, etc.); an equally reduced powerparameter (e.g., indicating permission to throttle L2 EVSEs into L1EVSEs to curtail equally among a set of EVSE, etc.); a separatelyreduced power parameter (e.g., throttling L2 EVSEs into L1 EVSEsindividually and separately from the set of EVSEs); and acondition-based parameter associated to a set of data that can informbattery level needed based on battery level condition of an expectedroute or job (e.g., using telematics data, such as vehicle data,including battery level, destination data for a plan route, origin datato indicate current location, and any other suitable data, etc.). In anexample, a condition-based parameter can include charging to meet arequired battery level for a job or route. The battery level needed(e.g., to complete the next job and/or route and come back to the baselocation) can be based on one or more of the total travel distance(e.g., collected from driver and/or job management system, etc.); theweather condition (via online weather sources, etc.); terrain (via thirdparty data, online sources, etc.); load weight (obtained from user orjob management system, etc.); and/or driver driving efficiency (e.g.,calculated from real time battery data and distance travelled). In aspecific example, implementing a condition-based power distribution typecan include intelligently distributing power by determining the batterylevel needed based on the difference between current battery level andthe needed battery level for the next job or route. In a specificexample, as shown in FIG. 9 , fleet management can include predictingenergy (e.g., in kWhs) for one or more fleet jobs (e.g., predictingenergy needed for a fleet job paired with a unique driver, etc.).

However, reservation parameters (e.g., reservation parameters forreserved charging sessions; ad hoc reservation parameters; etc.) can beconfigured in any suitable manner.

A reservation request is preferably received after (e.g., in responseto; at a time after; etc.) a submission of the reservation request by anentity (e.g., by a user at a user device; etc.), but reservationrequests can additionally or alternatively be received at any suitabletime relative portions of embodiments of the method 100, and/or at anysuitable time. In a specific example, a reservation request is receiveddirectly following a submission of a reservation request by a user at amobile application for a user device. In a specific example, for areservation request submitted directly at an EVSE operating in adisconnected mode (e.g., without connectivity to a centralizedreservation system; without connectivity to a calendar for reservationsat the EVSE; etc.), the reservation request can be received atcentralized reservation system after the EVSE is able to re-connect.

However, receiving a reservation request S110 and/or S310 can beperformed in any suitable manner.

2.2 Scheduling a Reserved Charging Session.

Embodiments of the method 100 can include scheduling one or morereserved charging sessions S120, which can function to reserve one ormore charging sessions at one or more EVSEs and/or charging locationsfor one or more electric vehicles.

Charging sessions (e.g., a session for charging an electric vehicle;etc.) can include a reserved charging session, an ad hoc chargingsession (e.g., a charging session requested and/or implemented for acurrent, ad hoc time period; etc.), and/or other suitable types ofcharging sessions. A reserved charging session preferably includes acharging session that is reserved and scheduled ahead of the time periodof charging. A reserved charging session is preferably associated with ascheduled time period during which charging of the electric vehicleoccurs.

Scheduling one or more reserved charging sessions is preferably based onone or more reservation requests. Scheduling one or more reservedcharging sessions can include processing one or more reservationparameters from one or more reservation requests, such as in order toschedule a reserved charging session according to the one or morereservation parameters. In an example, scheduling one or more reservedcharging sessions can include scheduling a reserved charging session fora scheduled time period and an EVSE (and/or charging location) indicatedby the set of reservation parameters from a received reservationrequest.

In a specific example, a reservation request can include a geographicaldestination parameter (e.g., coordinates and/or a destination selectedby a user and/or other suitable entity; etc.), where scheduling areserved charging session can include determining a reserved chargingsession location (e.g., associated with an EVSE to be used for thecharging session; etc.) based on the geographical destination parameter(e.g., where the reserved charging session location can be proximaland/or at the same location of the geographical destination; etc.)and/or scheduling the reserved charging session for the reservedcharging session location. A reserved charging session location caninclude the location of a single EVSE (e.g., where the user is directedto use the single EVSE for the reserved charging session; etc.), thegeneral location of a plurality of EVSEs (e.g., where the user canselect an EVSE to use from the plurality of EVSEs; etc.), and/or anysuitable locations associated with the reserved charging session. Inspecific examples, determining a reserved charging session location canbe based on distance between the reserved charging session and thegeographical destination indicated by the geographical destinationparameter; availability of one or more EVSEs at the reserved chargingsession location and/or at other suitable charging session locations(e.g., other proximal charging session locations; etc.); user data(e.g., user eligibility for a charging session at the reserved chargingsession location and/or other suitable charging session location; etc.);electric vehicle data; EVSE reservation parameters; other reservationparameters from a reservation request; and/or any other suitable data.However, scheduling one or more reserved charging sessions based on oneor more reservation requests can be performed in any suitable manner.

Alternatively, scheduling one or more reserved charging sessions can beperformed independent of a reservation request, such as where a reservedcharging session is automatically scheduled (e.g., based on a set ofpredefined rules; by a centralized reservation system; etc.). In aspecific example, recurring reserved charging sessions can beautomatically scheduled based on one or more parameters for a recurringreservation (e.g., where parameters can indicate time interval forrecurring reservations, such as daily, weekly, etc.; any suitablereservation parameters; etc.).

Scheduling one or more reserved charging sessions is preferably based onand/or associated with one or more EVSE reservation parameters. An EVSE(and/or set of EVSEs; and/or a charging location; etc.) is preferablyassociated with a set of EVSE reservation parameters for implementingone or more reserved charging sessions and/or ad hoc charging sessions.EVSE reservation parameters can include any one or more of: maximumsession duration parameters (e.g., indicating a maximum charging sessionduration; etc.); minimum session duration parameters (e.g., indicating aminimum charging session duration; etc.); early check in limitparameters (e.g., indicating guidelines for when a user checks in earlyrelative to a reservation start time for a reserved charging session;etc.); overstay penalty parameters (e.g., indicating guidelines for whena user overstays after a reservation end time for a reserved chargingsession; such as requiring payment of $1 per minute stayed after thereservation end time and/or requiring payment of any suitable amount;etc.); cancellation penalty parameters (e.g., indicating guidelines forwhen a reserved charging session is cancelled; such as charging amonetary penalty for cancelling a reserved charging session within athreshold time period before the reservation start time; etc.);disconnected mode parameters (e.g., indicating guidelines for operationin a disconnected mode in response to connectivity issues with an EVSE,such as connectivity issues between an EVSE and a correspondingcloud-based calendar for scheduling reserved charging sessions; etc.);reservation grace period parameters (e.g., indicating guidelines forwhen a user has not checked in and the time is after the reservationstart time; indicating a hold time where a reservation is cancelled if auser has not checked in within the hold time after reservation starttime; etc.); dynamic access parameters; and/or any other suitableparameters.

In a specific example, an EVSE is associated with a set of EVSEreservation parameters for implementing the reserved charging session,where the set of EVSE reservation parameters includes: a maximum sessionduration, a minimum session duration, an early check in limit, anoverstay penalty, and a cancellation penalty.

In a specific example, a first EVSE is associated with a first set ofEVSE reservation parameters for implementing a first reserved chargingsession, and where the first set of EVSE reservation parametersincludes: a first maximum session duration, a first minimum sessionduration, and a first early check in limit (e.g., where causing the EVSEto charge the electric vehicle includes causing the EVSE to charge theelectric vehicle in accordance with the first set of EVSE reservationparameters and/or in association with the scheduled time period; etc.).In the specific example and/or other specific examples, the method 100can include receiving a second reservation request; scheduling a secondreserved charging session based on the second reservation request, wherea second EVSE is associated with a second set of EVSE reservationparameters including a second maximum session duration distinct from thefirst maximum session duration, a second minimum session durationdistinct from the first minimum session duration, and a second earlycheck in limit distinct from the first early check in limit; determininga second check in (e.g., of the second electric vehicle; etc.) at thesecond EVSE for the second reserved charging session; and/or causing thesecond EVSE to charge the electric vehicle (e.g., in response todetermining the second check at the second EVSE for the section reservedcharging session; etc.) in accordance with the second set of EVSEreservation parameters, such as based on a second integration with thesecond EVSE.

In examples, the minimum session duration parameter can be used indetermining whether or not to allow an ad hoc charging session orreserved charging session when there is an already-scheduled, upcomingreserved charging session. In a specific example, an EVSE can beassociated with a minimum session duration parameter indicating aminimum charging session duration for a charging session at the firstEVSE, where the method 100 can include determining eligibility for an adhoc charging session at the first EVSE during an ad hoc time periodprior to the scheduled time period, such as based on a comparisonbetween the minimum charging session duration and a time differencebetween the ad hoc time period and the scheduled time period. In aspecific example, a reserved charging session and/or ad hoc chargingsession can be allowed if the time until an already-scheduled, upcomingreserved charging session is greater than (or equal to) the minimumsession duration indicated by the minimum session duration parameter. Inan example, the minimum session duration parameter can additionally oralternatively be used in creating reservation slots, such as for use ina user interface for allowing users to select reservation slots based onavailability. However, the minimum session duration parameter can beconfigured in any suitable manner and can be used in any suitable mannerfor determining eligibility for an ad hoc charging session.

In examples, the early check in limit parameter can be used indetermining whether a user (e.g., a user who has checked in prior totheir reserved charging session start time; etc.) is able to start acharging session (e.g., an ad hoc charging session; a shifted reservedcharging session; etc.) before their reserved charging session. In aspecific example, an EVSE can be associated with an early check in limitparameter indicating a reservation modification to be performed based ona time difference between a reservation check in time and a reservationstart time for a future reserved charging session. In examples, thereservation modification can include at least one of cancellation of thefuture reserved charging session and shifting of the reservation starttime for the future reserved charging session reserved charging session.In specific examples, the reservation modification can be performedbased on (e.g., in response to; etc.) the time difference (e.g., betweena reservation check in time and a reservation start time; etc.)exceeding the scheduled duration of the reserved charging session, butcan additionally or alternatively be based on any suitable comparison ofthe time difference to any suitable time period; and/or based on anysuitable time thresholds. However, the early check in parameter can beconfigured in any suitable manner.

One or more EVSEs can be associated with dynamic access parametersspecifying who can access the one or more EVSEs (e.g., which accessgroups can access the EVSEs; etc.), when the one or more EVSEs can beaccessed by users eligible to access the one or more EVSEs, how the oneor more EVSEs can be accessed (e.g., different pricing for differentusers; etc.), and/or other suitable access-related aspects. Dynamicaccess parameters can specify one or more access groups indicating theuser(s) (e.g., categories of users; etc.) that can access a given EVSE.Different access groups can be associated with different pricing (e.g.,a user will be able to access pricing specific to the access group thatthe user belongs to; etc.). In a specific example, a fleet site charginglocation (e.g., including a plurality of EVSEs, etc.) can be associatedwith dynamic access parameters specifying access restriction on theEVSEs during business hours, where only the fleet and employee accessgroups can access the EVSEs. In a specific example, the fleet accessgroup can access the EVSEs at no cost (e.g., free charging), theemployee access group can access the EVSEs at a charging pricing of$1/hr, where the EVSEs are open to the general public (e.g., notrestricted to fleet and employee access groups; etc.) duringnon-business hours, and where the general public can access the EVSEs ata charging pricing of $3/hr. However, any suitable access groups can bespecified for accessing any suitable EVSEs at any suitable time periodsand at any suitable pricing.

In variations, access groups can be associated with one or more accesscodes. In a specific example, the access code allows the specific accesscapabilities corresponding to the access group (e.g., ability to charge,specific pricing, specific EVSE reservation parameters such as maximumsession duration, etc.). Different access groups can be associated withdifferent access codes. Access codes can be unique to access groups;additionally or alternatively, same access codes can provide access todifferent access groups. In response to users attempting to access arestricted EVSE and/or restricted charging location (e.g., associatedwith dynamic access parameters; etc.), a user profile can be analyzed(e.g., using a mobile application, other applications, etc.) for one ormore relevant access codes that will provide the user with access. If auser profile does not include a relevant access code (and/or in anysuitable scenarios), a user can be prompted (e.g., via the mobileapplication, other applications, the EVSE, etc.) to input the accesscode to gain access. In a specific example, a user only needs to enterthe relevant access code once per charging location to gain and retainaccess.

In variations, morse code communication (e.g., a morse code handshake)between one or more electric vehicles and one or more EVSEs can beimplemented (e.g., based on ISO 15118 standard and/or any other suitablestandards and/or protocols, etc.). In examples, a morse code can becommunicated from an electric vehicle to an EVSE for authenticationallowing plug-in and charge. In examples, an access code can becommunicated to the EVSE by the electric vehicle.

A charger management system (e.g., that controls the electric vehicleand EVSE in a charging session) can issue a random 0 and 1 pattern asthe access code (e.g., authentication code, etc.) for an electricvehicle (e.g., via the mobile application, other applications, the EVSE,etc.), such as where the access code is required to be communicated bythe electric vehicle to the EVSE to complete authentication. In specificexamples, an electric vehicle can communicate a 1 by activating itsbuilt-in charger, thus allowing charging, and communicate a 0 bydeactivating its built-in charger, or vice versa (e.g., via electricvehicle or vehicles capable of programmable start/stop charging, etc.).In a specific example, upon arrival for a charging session, the electricvehicle executes the 0 and 1 pattern by turning on and off its built-incharger (via programmable start/stop charging, etc.). The chargermanagement system can detect the sequential activation and deactivationof the electric vehicle's built-in charger (e.g., by detecting chargingof the electric vehicle when charging is allowed, and vice versa, etc.),where authentication can be completed upon detection of the correctcode. Optionally, other characters may be communicated using 0's and 1'svia Morse code. A new code of 0's and 1's can be generated for everycharging session for improved security.

In a specific example, determining a check in can include generating, bya charger management system, a code (e.g., access codes, authenticationcodes, etc.), wherein the code includes a data sequence uniquelyidentifying the electric vehicle; causing the electric vehicle tocommunicate the code to the EVSE upon plugin of an EVSE into an electricvehicle; and wherein the check in is successful upon receiving, by theEVSE, the code as generated.

In specific examples, different 0 and 1 patterns can be generated fordifferent charging session scenarios in order to improve security. In aspecific example, a “00110” code can be issued for an electric vehicle,where the code is required to be communicated by the electric vehicle tothe EVSE to complete authentication, and where each “1” in the code iscommunicated by the electric vehicle by activating its built-in charger,and where each “0” in the code is communicated by the electric vehicleby deactivating its built-in charger.

In a specific example, a charger management system can allow chargingfor 5 minutes (and/or any suitable amount of time, such as based on thecharging session parameters and associated data), where the electricvehicle is expected to communicate the issued Morse code to the EVSE,and where charging will stop after 5 minutes (and/or any suitable amountof time) if the correct code is not communicated.

In a specific example, as shown by FIG. 8 , users can be grouped intodifferent access groups (e.g. user groups; groups such as staff,faculty, fleet, student, public, and/or other suitable groups, such as agroup associated with a set of electric vehicles) for dynamic accesscontrol. Codes (e.g., data sequence uniquely identifying an accessgroup, access codes, authentication codes, etc.) can be generated fordifferent user groups where such codes can be shared across the set ofvehicles. The codes can be refreshed (e.g., on a periodic interval, suchas daily, etc.). The codes can then be associated with an accessparameter placed on a user group. The access parameter can include apricing parameter specifying a pricing category (e.g., no charge,employee/fleet rate, student rate, public rate, etc.) for the accessgroup, and/or a dedicated time slot parameter assigning dedicatedcharging access to different time slots. However, user groups can beconfigured in any suitable manner.

In variations, users can gain access to a particular access groupthrough a request process, such as where users can request access to anaccess group, and an admin (e.g., host, etc.) can grant access to theaccess group. In specific examples, an admin sets access restricted timeranges, and for each access restricted time range, the admin can add oneor more access groups to the time range, indicating the users in theseaccess group(s) that are allowed to access the EVSE(s) (e.g., via ad hoccharging sessions and/or reserved charging sessions, etc.).

Access groups can be associated with one or more access codes and/or oneor more whitelists. Additionally or alternatively, access groups can beassociated with one or more blacklists (e.g., indicating users, accessgroups, and/or other entities who are restricted from charging).However, access groups and dynamic access parameters can be configuredin any suitable manner.

In examples, cancellation of one or more reserved charging sessions canbe performed by one or more of: a residential host, a site host (e.g.,manager; etc.), a user (e.g., associated with the electric vehicle;etc.) and/or any other suitable entities.

EVSEs can include any suitable types of EVSEs. Types of EVSEs can differbased on appearance; access method (e.g., RFID; network account viaapplication such as mobile application; credit card module; pluginwithout authentication; etc.); charging speed (e.g., level 1/L1, whichcan generally be residential or commercial, and/or can include a regularwall outlet such as one providing 120V, AC, adding around 5 miles/hourof charging for plugin hybrids; level 2/L2, which can generally beresidential or commercial, and/or can provide 220V-240V, AC, powervarying from 6.6 kW to 20 kW, adding around 20 miles or more/hour ofcharging; level 3/L3, which can generally be commercial or public,and/or can be DC, power of 25 kW or above; etc.); corresponding networkoperator; corresponding hardware original equipment manufacturer (OEM);and/or other suitable features.

Different types of EVSEs can include and/or be associated with same ordifferent types of EVSE reservation parameters, and/or same or differentvalues for types of EVSE reservation parameters. For example, EVSEs withhigher power (e.g., 25 kW and above; etc.) can be associated withshorter maximum session duration parameters compared to EVSEs with lowerpower. In a specific example, a L3 EVSE can be associated with a maximumsession duration of 45 minutes or less. In a specific example, a L2 EVSEcan be associated with a maximum session duration from 2 hours to 4hours. In examples, shorter maximum session durations can encouragehigher turnover, but maximum session durations that are too short canlead to poor user experiences. However, any suitable EVSEs can includeand/or be associated with any suitable EVSE reservation parameters.

Embodiments of a method 100 can include infrastructure management, whichcan include monitoring, collecting, and/or otherwise processing datafrom one or more EVSEs and/or other suitable hardware. However,infrastructure management can be performed in any suitable manner.

Embodiments of a method 100 can include community management (e.g., usermanagement). Community management can include setting EVSE reservationparameters (e.g., rules, etc.) regarding how one or more EVSEs can beused. Community management admins (e.g., hosts, etc.) preferably setEVSE reservation parameters for the one or more managed EVSEs, but anysuitable entities can be given access to set EVSE reservationparameters. In specific examples, EVSE reservation parameters includingone or more of maximum session duration, how many chargers arereservable, overstay penalty, and/or other suitable EVSE reservationparameters can be set for one or more EVSEs. Communities (e.g., that canbe managed) can include one or more charging locations and/or one ormore EVSEs. Different communities can be associated with different typesof hardware (e.g., different types of EVSEs; different EVSE types withdifferent charging speeds; EVSEs synced with solar production; etc.),different user groups (e.g., fleet, employees, contractors; differentaccess groups; etc.), where such differences can correspond to differentEVSE reservation parameters. In a specific example, in communities withvery cold or hot weather where battery performance drops, a longermaximum session duration can be established. In a specific example, in acommunity location with high traffic where a community management admindesires a higher turnover, a shorter maximum session duration can beestablished. However, community management can be performed in anysuitable manner.

Scheduling one or more reserved charging sessions is preferablyperformed with a reservation system (e.g., a centralized reservationsystem; etc.), but can additionally or alternatively be performed by anysuitable components (e.g., by an EVSE for scheduling a charging sessionat that EVSE, such as based on a reservation request submitted directlyat the EVSE; etc.).

Scheduling a reserved charging session for an EVSE (e.g., a single EVSEunit at a single location; etc.), can include updating a calendar forthe EVSE with suitable reservation parameters, reserved charging sessiondata (e.g., the scheduled time period for the reserved charging session;etc.), and/or other suitable data (e.g., user data; electric vehicledata; etc.). In specific example, each EVSE can be associated with theirown calendar that can be used for facilitating reserved chargingsessions and/or ad hoc charging sessions.

An EVSE reservation calendar is preferably cloud-based (e.g., availableon-demand via Internet connectivity; etc.). In specific examples, thecalendar can be updated (e.g., via one or more APIs) and/or otherwisemodified by one or more applications (e.g., a plurality of applicationsthrough which reservation requests and/or modifications can be made;etc.). In specific examples, the calendar can account for historic,current, and future charging sessions. In variations, a set of EVSEsand/or a charging location (e.g., a charging location where a pluralityof EVSEs reside; etc.) can share one or more calendars.

In a specific example, an EVSE can be associated with a single,cloud-based calendar for tracking ad hoc charging sessions and a set ofreserved charging sessions (e.g., including any suitable reservedcharging sessions for the EVSE; etc.). EVSEs can be operated in one ormore disconnected modes (e.g., when there are connectivity issuesbetween the EVSE and a corresponding cloud-based reservation calendar;etc.). A disconnected mode can be implemented based on one or moredisconnected mode parameters associated with an EVSE. In an example, anEVSE is operable in a disconnected mode in response to a connectivityissue (e.g., in response to not being able to establish communicationbetween a centralized reservation system and the EVSE; in response tolack of expected updates for the calendar from the associated EVSE;etc.) between the EVSE and the single, cloud-based calendar associatedwith the EVSE. In specific examples, operating the EVSE in thedisconnected mode can include at least one of: allowing ad hoc chargingsessions (e.g., in a mode only allowing for ad hoc charging sessions andnot reserved charging sessions; etc.) and/or canceling the set ofreserved charging sessions (e.g., cancelling currently reserved chargingsessions for the EVSE; preventing future scheduling of reserved chargingsessions, such as until connectivity with the EVSE is re-established;etc.); facilitating implementation of the set of reserved chargingsessions (e.g., facilitating implementation of already-scheduledreserved charging sessions; such as when the EVSE has sufficiently localcompute and memory to carry out such charging sessions; etc.) and/orpreventing scheduling of future reserved charging sessions; shuttingdown the EVSE; and/or any other suitable actions.

However, calendars (e.g., EVSE-associated calendars; etc.) forfacilitating charging sessions can be configured in any suitable manner.

Scheduling one or more reserved charging sessions is preferablyperformed after (e.g., in response to; at a time after; etc.) receivingone or more reservation requests, but can additionally or alternativelybe performed automatically (e.g., independent of a reservation request;etc.), and/or at any suitable time relative portions of embodiments ofthe method 100, and/or at any suitable time.

However, scheduling one or more reserved charging sessions S120 can beperformed in any suitable manner.

2.3 Determining a Check in.

Embodiments of the method 100 and/or 300 can include determining one ormore check ins for one or more charging sessions S130 and/or S330, whichcan function to identify when a user, electric vehicle, and/or otherentity has arrived for a given charging session.

Determining one or more check ins is preferably performed or one or morereserved charging sessions, but can additionally or alternatively beperformed for any suitable type of charging sessions (e.g., ad hoccharging sessions; etc.).

A check in preferably indicates that an electric vehicle associated witha reserved charging session is ready to be charged (e.g., an EVSE isplugged into the electric vehicle; the electric vehicle is at thelocation of the EVSE, such as a selected EVSE and/or an EVSE associatedwith a determined charging location; etc.). Additionally oralternatively, a check in can indicate that a user has arrived at anEVSE and/or charging location corresponding to a reserved chargingsession, and/or can a indicate any other suitable information.

Determining a check in preferably includes determining one or more of acheck in time (e.g., which can be compared to an early check in limitparameter if the check in time is prior to the corresponding reservationstart time; which can be compared to a reservation grace periodparameter if the check in time is after a corresponding reservationstart time; etc.); user data (e.g., indicating the user who is checkingin; etc.); electric vehicle data (e.g., indicating the electric vehicleto be charged during the reserved charging session; etc.); EVSE data(e.g., physical identifier and/or other suitable identifier of the EVSEthat a user has checked in at, such as for when a plurality of EVSEs atone or more charging locations are eligible to be used by the user for areserved charging session; etc.); and/or any other suitable data.

Determining one or more check ins can be based on one or more of: userinput at a user device (e.g., user inputs, at a mobile application,indicating that the user has checked in and/or arrived at an EVSE and/orcharging location associated with a reserved charging session; etc.);user location (e.g., based on location of a user device at and/orproximal an EVSE and/or charging location associated with a reservedcharging session; etc.); user input at an EVSE; plugin of an EVSE intoan electric vehicle; and/or any other suitable data indicative of a usercheck in for a charging session.

Determining one or more check ins is preferably performed by areservation system (e.g., a centralized reservation system; areservation system receiving check in indications from user devices,electric vehicles, EVSEs, and/or other suitable components; etc.), butcan additionally or alternatively be performed by any suitable entities.

Determining a check in for a reserved charging session is preferablyperformed after scheduling the reserved charging session (e.g., wherecheck ins are for reserved charging sessions that have been scheduledbeforehand, etc.), but can additionally or alternatively be a performedat any suitable time relative portions of embodiments of the method 100,and/or at any suitable time.

However, determining a check in for a reserved charging session S130and/or S330 can be performed in any suitable manner.

2.4 Causing Charging of an Electric Vehicle.

Embodiments of the method 100 can include causing charging of one ormore electric vehicles for one or more reserved charging sessions S140,S340, and/or S350, which can function to provide charging in one or morereserved charging sessions.

Causing charging of one or more electric vehicles is preferablyperformed by causing one or more EVSEs to charge the one or moreelectric vehicles, but can additionally or alternatively be performedwith any other suitable components.

Causing charging of one or more electric vehicles is preferably based onone or more integrations with one or more EVSEs. In examples, anintegration (e.g., of the reservation system; etc.) with one or moreEVSEs can allow remote communication (e.g., wireless communication;etc.) between the one or more EVSEs and another component (e.g.,reservation system; etc.). In specific examples, integrations with oneor more EVSEs can be based on one or more of: the Open Charge PointProtocol (OCPP) (e.g., for supporting communication between EVSEs and acentral management system network; etc.), the Open Charge PointInterface protocol (OCPI) (e.g., for supporting connections betweenmobility service providers such as entities having electric vehicledrivers as customers, and Charge Point operators such as managers ofEVSEs; etc.); and/or any other suitable protocols. In a specificexample, an integration with one or more EVSEs can include anintegration, via OCPI, with the network who can forward commands (e.g.,control signals; etc.) to corresponding EVSEs.

Controlling (e.g., remotely controlling; etc.) one or more EVSEs caninclude issuing one or more of: start charging commands (e.g., a“remoteStart” API call through OCPI, where the API call can result in acontrol signal being forwarded by the network to one or more EVSEs; forthe EVSE to begin charging of an electric vehicle; such as in responseto determining a check in of a user for a reserved charging sessionassociated with the EVSE; etc.); stop charging commands (e.g., a“remoteStop” API call through OCPI, where the API call can result in acontrol signal being forwarded by the network to one or more EVSEs; forthe EVSE to stop charging of an electric vehicle; such as in response toa current time reaching a reservation end time; such as in response to afully charged state of the electric vehicle; etc.); and/or any othersuitable commands (e.g., for requesting data, such as charging sessiondata for updating a calendar associated with the EVSE; etc.).

In a specific example, causing the EVSE to charge an electric vehicle(e.g., for an ad hoc charging session; etc.) based on an integrationwith the EVSE can include remotely issuing a first start chargingcommand to the EVSE; and where causing the EVSE to charge an electricvehicle (e.g., a different electric vehicle; a same electric vehicle;etc.) (e.g., for a reserved charging session; etc.) based on anintegration with the EVSE can include remotely issuing a second startcharging command to the EVSE.

In variations, for a given reserved charging session, a plurality ofEVSEs (e.g., a plurality of EVSEs in a single charging location; etc.)can service an electric vehicle associated with the reserved chargingsession. In a specific example, a user scheduled for a reserved chargingsession at a charging location including a plurality of EVSEs is notlimited to use of a single EVSE of the plurality of EVSEs for thereserved charging session. In a specific example, a user can use anysuitable available EVSE for a charging session at a charging locationincluding a plurality of EVSEs. In a specific example, a charginglocation including a plurality of EVSEs can specify that a predeterminednumber of the plurality of EVSEs (e.g., a predetermined number that isless than the number of EVSEs in the plurality of EVSEs; etc.) are to bemade available for reserved charging sessions (e.g., x number of EVSEsallotted to serving reserved charging sessions out of y number of totalEVSEs for the charging location; etc.), and/or the remaining number ofEVSEs are to be made available on a first come first served basis (e.g.,y number of total EVSEs minus x number of EVSEs allotted to servingreserved charging sessions; etc.). In a specific example, thepredetermined number of the plurality of EVSEs allotted for reservedcharging sessions can correspond to any suitable EVSEs of the pluralityof EVSEs (e.g., specific EVSEs are not specified; etc.), where a usercan select any available EVSE of the plurality of EVSEs for a reservedcharging session (e.g., such as long as the number of EVSEs servingreserved charging sessions is equal to the predetermined number, x, ofEVSEs allotted to serving reserved charging sessions at the charginglocation; etc.). Alternatively, the predetermined number of theplurality of EVSEs allotted for reserved charging sessions cancorrespond to specified EVSEs (e.g., specified by a site host, acommunity management admin, etc.).

Causing an EVSE to charge an electric vehicle can be based on a physicalidentifier (and/or other suitable identifiers) for the EVSE. Thephysical identifier can be physically present at the EVSE (e.g., on theEVSE; etc.), can be unique to the EVSE, and/or can otherwise beconfigured. One or more physical identifiers can be mapped to one ormore virtual identifiers (e.g., stored at a reservation system inassociation with the EVSE; etc.), but can additionally or alternativelyassociated with any suitable components. Causing an EVSE to charge anelectric vehicle based on a physical identifier can include selectingthe EVSE to remotely issue a command to based on the physical identifierof the EVSE. In a specific example, an EVSE can be from a set of EVSEsassociated with a charging location (e.g., where a single charginglocation includes a plurality of EVSEs; etc.), where each EVSE from theset of EVSEs corresponds to a unique physical identifier, where remotelyissuing a first start charging command includes remotely issuing thefirst start charging command to the EVSE based on the physicalidentifier for the EVSE. In the specific example and/or other suitablespecific examples, remotely issuing a second start charging command caninclude remotely issuing the second start charging command to the EVSEbased on the physical identifier for the EVSE.

In examples, a user can provide a physical identifier (e.g., for an EVSEselected by a user from a set of EVSEs associated with a single charginglocation; etc.). Users can provide physical identifiers through one ormore of: a user device (e.g., through an application for the userdevice; etc.), an EVSE (e.g., through an EVSE interface; etc.), anelectric vehicle, and/or any other suitable components. In a specificexample, the method 100 can include prompting a user to provide thephysical identifier for the EVSE selected by a user from the set ofEVSEs (e.g., of a single charging location; etc.) for the reservedcharging session; and/or receiving the physical identifier for the EVSEfrom the user. Additionally or alternatively, an EVSE physicalidentifier and/or other suitable EVSE identifiers can be automaticallycollected (e.g., based on a plug-in of the EVSE charger to the electricvehicle, etc.). EVSE identifiers and/or other suitable identifiers canbe collected from EVSEs, electric vehicles (e.g., plugged-in with anEVSE; etc.), mobile devices (e.g., mobile phones, etc.), users, and/orany other suitable entities.

Causing an EVSE to charge an electric vehicle can be based on a powerdistribution type associated with one or more reservation parametersand/or other suitable parameters. There can be a user opt-indistribution type for power distribution associated with the solarproduction parameter, the infrastructure-limitation parameter, and thetime-of-use parameter; a uniform power distribution type associated withthe equally reduced power reduction parameter and the separately reducedpower parameter; and a condition-based distribution type fordistributing power associated with the condition-based parameter. A useropt-in power distribution type causes the EVSE to dynamically throttlethe power output based on the associated reservation parameter (and/orother suitable reservation parameters that justifies throttling the EVSEto satisfy said reservation parameters). In specific examples, thereservation parameter can include one or more opt-in indications oropt-out indications for one or more power distribution types (e.g., apower reduction offered at a cheaper price. In examples, a uniform powerdistribution type causes the EVSE to throttle power equally among a setof EVSE (e.g., to keep total kW under a certain amount), or todeactivate individual EVSEs among a set of EVSE (e.g., deactivating anumber of EVSE among a set of EVSE to keep total kW under a certainamount, etc.).

In examples, a condition-based power distribution type causes the EVSEto charge the electric vehicle based on the battery level associatedwith (e.g., needed for; required by; correlated with; etc.) a route orjob (e.g., using telematics data, vehicle data, user data, and/or othersuitable data and parameters, etc.). In a specific example, acondition-based distribution type can intelligently distribute power bydetermining the battery level needed based on the difference betweencurrent battery level and the needed battery level for the next job orroute, and causing the EVSE to charge the electric vehicle for theneeded battery level. A condition-based power distribution type canadditionally or alternatively be used to plan for a road trip (viamobile applications, etc.), whereby optimal charging stops can bedetermined based on battery level needed for the subsequent chargingstop (e.g., using telematics data such as including one or more ofdriver driving efficiency, total driving distance between chargingstops, EVSE data indicating current availability, etc.).

In a specific example, user opt-in distribution types can be implementedfor non-fleet users and/or scenarios, and condition-based powerdistribution types can be implemented for fleet users and/or scenarios.

However, power distribution types can be configured in any suitablemanner.

In a specific example, causing the EVSE to charge an electric vehicle(e.g., for an ad hoc charging session; etc.) in accordance with a powerdistribution type based on an integration with the EVSE can includeremotely issuing a start charging command to the EVSE; where causing theEVSE to charge an electric vehicle (e.g., a different electric vehicle;a same electric vehicle; etc.) (e.g., for a reserved charging session;etc.) based on an integration with the EVSE can include remotely issuinga continue charging command in accordance with a power distribution typefor the charging session; and where causing the EVSE to continuecharging based on an integration with the EVSE can include remotelyissuing a throttle power output command for the EVSE in accordance withthe power distribution type and/or access parameters.

In variations, electric vehicle location can be used in facilitatingaccess and/or authentication. For example, if an electric vehiclearrives (e.g., tracked using vehicle location, etc.) proximal (e.g., at,etc.) an EVSE location within a threshold time period for a chargingsession (e.g., a reserved charging session where the electric vehicle isexpected to arrive at the location and time; etc.), then access and/orauthentication can be automatically granted (e.g., not requiring a morsecode handshake, etc.). In a specific example, if more than one vehiclearrives in a threshold time window, a morse code authentication processcan be used to differentiate the vehicles (e.g., where a short code,such as a 2-digit code, could be used).

In variations, group codes can be generated for a fleet, community,and/or other set of vehicles, where such a code can be shared across theset of vehicles. A group code can be refreshed (e.g., on a periodicinterval, such as daily, etc.). Communities can be associated withand/or include one or more of workplaces, multi-unit dwellings, schoolcampuses, hospitality, and/or other suitable community settings. Inspecific examples, group codes can be 3-digits in length and/or anysuitable length (e.g., shorter lengths; longer lengths to accommodatescenarios where a larger number of vehicles are expected to be at anEVSE site at the same time, where the longer group code can be used todifferentiate, etc.). In specific examples, group codes can beassociated with different access parameters (e.g., a pricing parameter,a dedicated time slot parameter, etc.) to allow for group and/ortime-specific pricing.

However, morse codes and associated authentication approaches can beconfigured in any suitable manner.

Causing charging of one or more electric vehicles is preferablyperformed by a reservation system (e.g., a centralized reservationsystem in remote communication with a set of EVSEs for issuing one ormore commands; etc.), but can additionally or alternatively be performedby any suitable components.

Causing charging of one or more electric vehicles is preferablyperformed after (e.g., in response to; etc.) determining a check in of auser for a reserved charging session (e.g., where an EVSE associatedwith the reserved charging session is caused to charge an electricvehicle for a user associated with the reserved charging session; etc.),but can additionally or alternatively be performed at any suitable timerelative portions of embodiments of the method 100, and/or at anysuitable time.

Causing charging of one or more electric vehicles can be based on (e.g.,dependent upon, etc.) determining payment (e.g., for the chargingsession; etc.) and/or authentication. Determining payment and/orauthentication can be performed by one or more of: a charger managementsystem, a reservation system, an application of a user device, an EVSE,and/or any other suitable components.

However, causing charging of one or more electric vehicles S140, S340,and/or S350 can be performed in any suitable manner.

2.5 Facilitating an Ad Hoc Charging Session.

Embodiments of the method 100 can additionally or alternatively includefacilitating one or more ad hoc charging sessions S150, which canfunction to guide and/or implement one or more ad hoc charging sessions.Additionally or alternatively, embodiments of the method 100 can preventone or more ad hoc charging sessions (e.g., in response to determinationof ineligibility of a user for an ad hoc charging session; etc.).

An ad hoc charging session preferably includes a charging session thatwas not reserved ahead of time, such as a charging session that is beingrequested for a current time at an EVSE and/or charging location, suchas at an EVSE and/or charging location that is proximal (e.g., nearby;at; etc.) a user location (e.g., determined based on a user devicelocation; etc.).

Facilitating one or more ad hoc charging sessions can additionally oralternatively include determining eligibility for an ad hoc chargingsession (e.g., for an electric vehicle at an EVSE; etc.) S152;accounting for an ad hoc charging session S154; causing an EVSE tocharge the electric vehicle for the ad hoc charging session S156; and/orany other suitable processes for facilitating one or more ad hoccharging sessions S150.

Determining eligibility for an ad hoc charging session S152 can functionto determine whether to allow an ad hoc charging session for a user.Determining eligibility for an ad hoc charging session is preferablybased on one or more reservation parameters (e.g., from a reservationrequest; etc.) and/or one or more EVSE reservation parameters.

In examples, determining eligibility for an ad hoc charging session canbe based on a comparison between an ad hoc time period (e.g., a currenttime period; a time associated with request of an ad hoc chargingsession by a user; etc.) and a scheduled time period. In a specificexample, determining eligibility for the ad hoc charging session basedon the comparison between the ad hoc time period and the scheduled timeperiod can include: determining a length of time difference between thead hoc time period and the scheduled period (e.g., where the length oftime difference can include the amount of time from a current time untilthe reservation start time for the next scheduled reserved chargingsession; etc.); and/or in response to the length of time differenceexceeding a first length of time difference threshold (e.g., apredetermined threshold, such as 30 minutes, 45 minutes, 60 minutes,etc.; an automatically determined threshold, such as based on theschedule of reserved charging sessions and/or other suitable variables;etc.), determining that a user (e.g., associated with the secondelectric vehicle, etc.) and/or other suitable entity is eligible for thead hoc charging session. In a specific example, determining eligibilityfor the ad hoc charging session based on the comparison between the adhoc time period and the scheduled time period can include: in responseto the length of time difference exceeding a second length of timedifference threshold (e.g., when the time until the upcoming reservedcharging session is sufficiently large, such as greater than the maximumsession duration for the EVSE; such as greater than an ad hoc timeperiod corresponding to a predicted ad hoc charging session durationindicated by a user input describing an end time and/or desired chargingsession duration for the ad hoc charging session; etc.), determiningthat a user (e.g., associated with second electric vehicle; etc.) and/orother suitable entity is eligible for the ad hoc charging session for aduration specified by a maximum session duration parameter associatedwith the EVSE. Determining eligibility for an ad hoc charging sessioncan include collecting one or more user inputs (e.g., in response toprompting the user for a user input, such as at a mobile applicationand/or at a vehicle application; etc.) describing an end time and/ordesired charging session duration for the ad hoc charging session, suchas where an ad hoc time period can be based on the one or more userinputs (e.g., desired ad hoc charging session duration and/or end time;etc.). Determining eligibility can include processing an ad hoc chargingsession as a reserved charging session associated with a reservationstart time parameter of the current time (e.g., now).

However, determining eligibility for an ad hoc charging session S152 canbe performed in any suitable manner.

Accounting for an ad hoc charging session S154 can function to track,record, and/or otherwise account for the ad hoc charging session, suchas to prevent scheduling of reserved charging sessions that wouldoverlap with the ad hoc charging session and/or a threshold time periodafter the ad hoc charging session. Accounting for one or more ad hoccharging sessions can include one or more of: updating EVSE calendars(e.g., for EVSEs used in the one or more ad hoc charging sessions;etc.); recording ad hoc charging session data; and/or any other suitableprocesses.

However, accounting for an ad hoc charging session S154 can be performedin any suitable manner.

Causing an EVSE to charge one or more electric vehicles for one or moread hoc charging sessions S156 can function to implement the ad hoccharging session with the EVSE.

Causing an EVSE to charge one or more electric vehicles for one or moread hoc charging sessions is preferably performed after (e.g., inresponse to; etc.) receiving a request for an ad hoc charging session(e.g., from a user at a user device; from a user via an EVSE interface;etc.), but can additionally or alternatively be performed at anysuitable time relative portions of embodiments of the method 100, and/orat any suitable time.

Causing an EVSE to charge one or more electric vehicles for one or moread hoc charging sessions S154 can be performed in any suitable manneranalogous to and/or similar to causing an EVSE to charge one or moreelectric vehicles for one or more reserved charging sessions S140.However, causing an EVSE to charge one or more electric vehicles for oneor more ad hoc charging sessions S156 can be performed in any suitablemanner.

Any suitable portions of facilitating one or more ad hoc chargingsession with an EVSE can be performed at any suitable time periodrelative facilitating one or more reserved charging sessions with theEVSE. In a specific example, an EVSE can be used in implementing a firstad hoc charging session, followed by a first reserved charging session,followed by a second ad hoc charging session, followed by a secondreserved charging session, etc. Additionally or alternatively, anysuitable number of ad hoc charging sessions and/or reserved chargingsessions can be implemented with an EVSE in any suitable order at anysuitable time (e.g., any suitable mixture of ad hoc charging session(s)and reserved charging session(s), etc.). However, facilitating one ormore ad hoc charging sessions can be performed at any suitable timerelative portions of embodiments of the method 100, and/or at anysuitable time.

Any suitable number of ad hoc charging sessions can be facilitated. In aspecific example, an EVSE can be used in implementing a plurality of adhoc charging sessions and a plurality of reserved charging sessions fora given time period (e.g., for a given day; etc.). In a specificexample, a first EVSE can be used in implementing an ad hoc chargingsession concurrently with a second EVSE used in implementing a reservedcharging session. However, any suitable number of EVSEs can implementany suitable number of ad hoc charging sessions and/or reserved chargingsessions concurrently, sequentially, and/or at any suitable time in anysuitable order.

However, facilitating one or more ad hoc charging sessions S150 can beperformed in any suitable manner.

2.6 Providing a User Interface.

Embodiments of the method 100 and/or 300 can additionally oralternatively include providing a user interface S160, which canfunction to provide users with means to communicate with a reservationsystem and/or other suitable components, such as for submitting,viewing, tracking, modifying, and/or otherwise using reservationrequests, check ins, payment, authentication, and/or other suitableprocesses.

Providing a user interface preferably includes providing a userinterface via a mobile application for a mobile user device, but one ormore user devices can additionally or alternatively be provided throughany suitable applications and/or for any suitable devices.

Providing a user interface can include providing a means for viewingEVSEs and/or charging locations on a map (e.g., where reservationrequests can be submitted for such EVSEs and/or charging locations;where information can be provided to the user regarding the EVSEs and/orcharging locations; etc.).

In a specific example, the method 100 can include providing a userinterface at a mobile application for a user device, where the userinterface includes a set of charging location indicators (e.g.,graphical indicators on a graphical map; any suitable indicators; etc.)associated with a set of EVSEs including the EVSE, where the reservationrequest is associated with a charging location indicator of the set ofcharging location indicators, where the charging location indicator isassociated with the EVSE.

In a specific example (e.g., in relation to an ad hoc charging session;etc.), the method 100 can include providing a user interface at a mobileapplication for user device of a user associated with an electricvehicle, where the user interface includes: a start charging buttonassociated with the ad hoc charging session, where the start chargingbutton is configured to graphically indicate the eligibility for the adhoc charging session (e.g., based on determining eligibility for the adhoc charging session S152; etc.); and/or a reservation button forsubmitting a reservation request for a reserved charging session.

In a specific example, the method 300 can include providing a userinterface at a mobile application for a user device, where the userinterface can include one or more of a map of the route, a set ofcharging location indicators associated with a set of EVSEs that havebeen determined to provide optimum charging (e.g. based on the batterylevel needed, the distance traveled, driver driving efficiency, and/orother telematics data, etc.), and/or a reservation button for submittinga user reservation request for a reserved charging session, wherein thereservation button can be configured to graphically indicate optimumcharging locations based on the battery level needed for the route.

However, providing one or more user interfaces S16 o can be performed inany suitable manner.

2.7 Providing a Notification.

Embodiments of the method 100 and/or 300 can additionally oralternatively include providing one or more notifications S170, whichcan function to inform and/or guide one or more users (e.g., drivers ofelectric vehicles, owners of electric vehicles, and/or otherwiseassociated with electric vehicles; etc.), hosts (e.g., managers of EVSEsand/or charging stations; etc.), and/or any other suitable entities.

Providing notifications preferably includes providing mobile devicenotifications (e.g., alerts, banners, notification center notifications,lock screen notifications; etc.), but providing notifications canadditionally or alternatively include providing notifications to anysuitable device and/or entity through any suitable means.

Notifications can include notifications for any suitable portions ofembodiments of the method 100, such as notifications for any suitableportions of a charging session (e.g., reserved charging session; ad hoccharging session; etc.). Notifications can include notifications tousers and/or hosts for one or more of: reservation scheduling (e.g.,notifications for successful reserving a of a reserved charging session;etc.); reservation cancellation (e.g., notifications for reservationcancellation by a host; notifications for reservation cancellation by auser; etc.); reservation approaching (e.g., notifications prior toreservation start time, where different notifications can be providedbased on the amount of time until the reservation start time;notifications that can be skipped if a user has checked in for areserved charging session; etc.); reservation start (e.g., notificationsat reservation start time, where such notifications can be skipped ifthe user has checked in for the reserved charging session; notificationsindicating that the reserved charging session will be canceled after athreshold amount of time if the user has not checked in; notificationsupon check in by the user for a reserved charging session; notificationsupon determining a connected EVSE to the electric vehicle and/orstarting of charging, where such notifications can indicate the amountof charging to occur in the charging session; etc.); early check in(e.g., notifications to a host for indicating electric vehicle data,billing data, user data, and/or other suitable information, such as ifthe EVSE is available for use; notifications if the EVSE is currentlyunavailable and in use; etc.); charging stopped (e.g., notifications inresponse to a driver unplugging the EVSE earlier than the reservationend time; notifications indicating that the electric vehicle is fullycharge; notifications in response to driver termination of a reservedcharging session before reservation end time; etc.); reservation ending(e.g., notifications indicating an upcoming reservation end time duringa reserved charging session; notifications indicating overstay penaltyfor staying past the reservation end time; where such notifications canbe skipped if the EVSE is unplugged from the electric vehicle; etc.);reservation completed (e.g., notifications indicating completion of areserved charging session; etc.); overstay (e.g., notifications based onthe overstay penalty associated with the EVSE; notifications indicatingthat the user has overstayed past the reservation end time, such asnotifications provided during an overstay and the EVSE is stillconnected to the electric vehicle; notifications encouraging the user tomove their electric vehicle; etc.); overstay and upcoming reservedcharging session (e.g., notifications for when a first user hasoverstayed past their reservation end time, and when a differentreserved charging session is upcoming or being blocked by the firstuser; notifications encouraging the overstaying user to move theirelectric vehicle; notifications provided at regular time intervals;etc.); vendor coupons (e.g., notifications for coupons offered by one ormore vendors; notifications to users who charged their electric vehicleor used an associated application on their user device near any EVSEswithin a suitable threshold distance from a vendor offering a coupon;etc.); new charger available (e.g., notifications to users describingthe new EVSE and/or associated information; etc.); events (e.g.,notifications for special events such as power outages; co-marketingactivities; etc.)

Notifications can include textual content (e.g., text-basedcommunications; any suitable font size, font color, font type; otherfont parameters; spacing parameters; etc.); graphical content (e.g.,communications including images, video, etc.); audio parameters (e.g.,audio-based communications such as through music, sound notifications, ahuman voice; any suitable volume parameters; tone parameters; pitchparameters; etc.); touch content; and/or any other suitable type ofcontent. Notification content can differ based on the type and/or formatof the notification. In a specific example, textual content can differbetween notifications for different stages and/or aspects of a chargingsession. In a specific example, textual content can differ betweenalerts and banners for the same stage and/or aspects of a chargingsession.

Providing notifications can be performed by a reservation system and/orby any other suitable components. Providing notifications can beperformed at any suitable items relative portions of embodiments of themethod 100, and/or at any suitable time and at any suitable frequency.

However, providing notifications S170 can be performed in any suitablemanner.

3. Other

Embodiments of the method 100, 300 and/or system 200 can include everycombination and permutation of the various system components and thevarious method processes, including any variants (e.g., embodiments,variations, examples, specific examples, figures, etc.), where portionsof embodiments of the method 100 and/or processes described herein canbe performed asynchronously (e.g., sequentially), concurrently (e.g., inparallel), or in any other suitable order by and/or using one or moreinstances, elements, components of, and/or other aspects of the system200 and/or other entities described herein.

Any of the variants described herein (e.g., embodiments, variations,examples, specific examples, figures, etc.) and/or any portion of thevariants described herein can be additionally or alternatively combined,aggregated, excluded, used, performed serially, performed in parallel,and/or otherwise applied.

Portions of embodiments of the method 100, 300 and/or system 200 can beembodied and/or implemented at least in part as a machine configured toreceive a computer-readable medium storing computer-readableinstructions. The instructions can be executed by computer-executablecomponents that can be integrated with embodiments of the system 200.The computer-readable medium can be stored on any suitablecomputer-readable media such as RAMs, ROMs, flash memory, EEPROMs,optical devices (CD or DVD), hard drives, floppy drives, or any suitabledevice. The computer-executable component can be a general orapplication specific processor, but any suitable dedicated hardware orhardware/firmware combination device can alternatively or additionallyexecute the instructions.

As a person skilled in the art will recognize from the previous detaileddescription and from the figures and claims, modifications and changescan be made to embodiments of the method 100, 300, system 200, and/orvariants without departing from the scope defined in the claims.Variants described herein not meant to be restrictive. Certain featuresincluded in the drawings may be exaggerated in size, and other featuresmay be omitted for clarity and should not be restrictive. The figuresare not necessarily to scale. The absolute or relative dimensions orproportions may vary. Section titles herein are used for organizationalconvenience and are not meant to be restrictive. The description of anyvariant is not necessarily limited to any section of this specification.

What is claimed is:
 1. A method for charging a first electric vehicle ata first Electric Vehicle Service Equipment (EVSE), the methodcomprising: receiving a reservation request from a first user at a firstuser device for a first charging session, wherein the first user isassociated with the first electric vehicle, and wherein the reservationrequest comprises at least one reservation parameter indicative of thefirst charging session for the first electric vehicle; determiningeligibility for a power distribution type for the first charging sessionat the first EVSE; determining a first check in at the first EVSE forthe first charging session; after determining the first check in at thefirst EVSE for the first charging session, causing the first EVSE tocharge the first electric vehicle in accordance with the powerdistribution type for the first charging session, based on anintegration with the first EVSE.
 2. The method of claim 1, whereincausing the first EVSE to charge the first electric vehicle inaccordance with the power distribution type comprises causing the firstEVSE to charge the first electric vehicle with reduced power based on aset of power distribution parameters comprising at least one of: a solarproduction parameter associated with solar production, aninfrastructure-limitation parameter associated with infrastructurelimitations, a time-of-use parameter associated with periods of highactivity and low activity, an equally reduced power parameter associatedwith throttling the power output equally for a set of EVSEs, aseparately reduced power parameter associated with throttling the firstEVSE separately from the set of EVSEs, and a condition-based parameterassociated with a battery level associated with a route.
 3. The methodof claim 2, wherein the power distribution type comprises at least oneof: a user opt-in distribution type for power distribution associatedwith the solar production parameter, the infrastructure-limitationparameter, and the time-of-use parameter; a uniform distribution typeassociated with the equally reduced power parameter and the separatelyreduced power parameter; and a condition-based distribution type fordistributing power associated with the condition-based parameter.
 4. Themethod of claim 2, causing the first EVSE to charge the first electricvehicle with reduced power in accordance with the power distributiontype comprises causing the first EVSE to charge the first electricvehicle with reduced power based on the condition-based parameter,wherein the method further comprises determining the battery levelassociated with the route based on a difference between a currentbattery level and a battery level needed in total to complete the route,and based on telematics data comprising at least one of: a totaldistance including a return route as required for charging, a weatherreport, a terrain condition, a load weight, and a driver drivingefficiency; wherein the driver driving efficiency is determined by thebattery level in real-time and the total distance traveled.
 5. Themethod of claim 2, further comprising: providing a user interface at amobile application, wherein the user interface comprises: a map of theroute, and a reservation button for submitting a user reservationrequest for a reserved charging session, wherein the reservation buttonis configured to graphically indicate optimum charging locations basedon the battery level associated with the route.
 6. The method of claim1, wherein determining the first check in comprises: generating a codeby a charger management system, wherein the code comprises a datasequence uniquely identifying the first electric vehicle; and causingthe first electric vehicle to communicate the code to the first EVSE,and wherein the check in is successful upon receiving, by the firstEVSE, the code.
 7. The method of claim 6, wherein the code comprises aMorse code, wherein causing the first electric vehicle to communicatethe code comprises allowing and disallowing a first electric vehiclecharger in sequence, wherein allowing and disallowing the first electricvehicle charger occurs periodically and for a duration corresponding tocommunication of the Morse code.
 8. The method of claim 1, whereindetermining the check in at the first EVSE comprises matching a charginglocation associated with the first EVSE with the vehicle locationcorresponding to the first electric vehicle.
 9. The method of claim 1,wherein causing the first EVSE to charge the first electric vehiclebased on the first integration with the EVSE comprises: remotely issuinga start charging command to the EVSE; and issuing a continue chargingcommand to the first EVSE, and a reduce power output command for thefirst EVSE based on the power distribution type.
 10. The method of claim1, wherein the power distribution type is a condition-based powerdistribution type determined from a battery level needed for a fleetjob.
 11. The method of claim 10, wherein causing the first EVSE tocharge the first electric vehicle according to the power distributiontype comprises determining the battery level needed for the fleet jobbased upon route of travel, vehicle data, and telematics data.
 12. Themethod of claim 1, wherein the first user comprises one of a fleet groupmember and a fleet management entity.
 13. The method of claim 1, whereindetermining eligibility for the power distribution type furthercomprises associating the first user with a dynamic access parameter fora fleet access group, and allowing the first user to charge the firstelectric vehicle based upon the dynamic access parameter.
 14. The methodof claim 13, wherein allowing the first user to charge the firstelectric vehicle comprises allowing charging with pricing specified forthe fleet access group.
 15. The method of claim 1, further comprisingrestricting access to the first EVSE by a second vehicle during businesshours of a fleet group, wherein the second vehicle is unassociated witha fleet access group.
 16. The method of claim 1 wherein, the powerdistribution type is associated with reduced power from the first EVSEfor the first charging session, and wherein the first charging sessionis associated with a demand response event.
 17. A method for charging afirst electric vehicle at a first Electric Vehicle Service Equipment(EVSE), the method comprising: receiving a reservation request from afirst user at a first user device for a first charging session, whereinthe first user is associated with the first electric vehicle, andwherein the reservation request comprises at least one reservationparameter indicative of the first charging session for the firstelectric vehicle; determining eligibility for a power distribution type,wherein the power distribution type is a condition-based powerdistribution type, for the first charging session at the first EVSE;determining a first check in at the first EVSE for the first chargingsession, wherein determining the first check in at the first EVSE forthe first charging session comprises issuing, via a charger managementsystem, a code for authentication between the first electric vehicle andthe first EVSE and receiving a communication of the code to the firstEVSE during the first check in; after determining the first check in atthe first EVSE for the first charging session, causing the first EVSE tocharge the first electric vehicle in accordance with the powerdistribution type for the first charging session, based on anintegration with the first EVSE.
 18. The method of claim 17, wherein thecode is an access code associated with a fleet group.
 19. The method ofclaim 17, wherein the power distribution type is determined from abattery level needed for a fleet job.
 20. The method of claim 17,wherein the code is a binary code.